home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 8
/
The Arsenal Files Collection #8 (Arsenal Computer) (1996).ISO
/
gen_bbs
/
dk-nodes.zip
/
NODES.DOC
< prev
next >
Wrap
Text File
|
1996-12-17
|
4KB
|
107 lines
Nodes Monitor for Telegard 3.00+
Version 0.01 alpha - 12/16/96
Disclaimer
----------
This program comes with no guarantees. If it damages, destroys
or modifies your system in any way you are ultimately responsible, not
me. I will not be held accountable for any damages to your life or your
property which arise from the use or misuse of this program. You have
been forewarned.
Purpose
-------
A sysop in the FidoNet Telegard Support echo asked if someone
would program a command-line utility which he could use to monitor the
activity of each node. I had just gotten back from my Grade 11 English
exam at 12:30 in the afternoon when I read his message. I was bored, so
I started coding... Now, at 2:00 in the morning I'm finally writing the
documentation for the program. I didn't spend ten hours on this
program; I spent about one. It wasn't difficult to code and I enjoyed
programming it.
Usage
-----
This program, when run from the command-line with the
appropriate parameters, will display the activity for each node which
exists in the NODES.DAT file. It will display the node number, the
user's name (or handle, if that option is turned on in the Telegard
configuration), what each node is doing, the logon time and the baud
rate. It will also display two flags, for users who are logged in as
invisible users or those who do not want to be disturbed. I don't know
if these options are supported in Telegard 3.02; they've been coded in
anyways.
Command-line parameters and the program's syntax are as follows:
NODES.EXE <full path to CONFIG.TG> <polling value>
The first parameter should point to where the CONFIG.TG file is
located. This is a _FULL_ path. Don't enter "C:\TG\" or anything like
that, have it point to "C:\TG\CONFIG.TG" or else it will not work.
The second parameter defines how long the program will wait
before each read of the NODES.DAT file. For example, if the polling
value was set to 20, the program would read in the NODES.DAT datafile
every 20 seconds. This parameter is optional. If it is not specified,
a value will be taken from CONFIG.TG and used instead. This value
corresponds to how long each node will wait before updating the
NODES.DAT file.
Examples:
NODES.EXE C:\TG\CONFIG.TG
- Load up the node monitor with the default value and
the specified file (C:\TG\CONFIG.TG)
NODES.EXE C:\TG\CONFIG.TG 5
- Load up the node monitor and have it use
C:\TG\CONFIG.TG as the BBS setup file. It will also
wait five seconds between each read of the NODES.DAT
file.
Multi-Node
----------
Obviously, this program uses multi-node routines. If you don't
have SHARE.EXE (or a similar program) loaded, I suggest you load it as
file locking will not work properly. I have tested this program to the
best of my abilities. If you have bugs, please send me the run-time
error number and the offset (eg. FFFF:FFFF) at which the error occurred.
If you can, I'd also like a description of what was going on at the time
of the error. I can be reached as folllows:
Name : Mustapha Mond, AKA Darkness
BBS : Pointbreak (613-569-0151)
FidoNet : 1:163/422
Internet : darkness@pointbrk.erkware.com
If you're a decent person...
----------------------------
This program wasn't a very big deal at all and is distributed as
freeware, but if you want to send me something for my troubles here's my
mailing address:
Pointbreak Systems
181 Second Avenue
Ottawa, Ontario
K1S 2H6
Feel free to send me money, postcards, letters suggesting
changes and reporting bugs, gift-certificates or coupons,
priceless works of art, expensive cars, etc... I can't give you anything
in return, but hey.. you'll make my day. :)
Planned Features
----------------
If I ever have another two hours of spare time on my hands I'll
see if I can program an editor for the NODES.DAT file into the node
monitor. I make no promises, though.
12/16/96